home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
os2
/
nef234.zip
/
WHATSNEW.TXT
< prev
Wrap
Text File
|
1996-05-20
|
46KB
|
1,087 lines
NEF
Changes and Additions
2.34 Public Release, May 20 1996
- Extension of the PassThru concept.
If you specify the "-0" flag in a FileArea definition,
when you do "Nef Clean", the files not currently
referenced in outbound attaches are deleted.
If you specify "-0<days>", the files in that area will
not be deleted until they become older than <days> _AND_
there is no file attach pointing to them.
Example:
FileArea Area1 \file\area1\ O -030 2:345/678 I123/4
Files in \file\area1 will be deleted when older than 30
days _and_ not referenced by any file attach.
- OS/2: New "KillDate Write|Creation" statement.
To specify the date to be used for evaluating the file
age that triggers the file deletion in passthru areas.
This statement is useful for HPFS, ignored on FAT.
If none specified, "Creation" is assumed.
Example:
KillDate Write
- New extended "-0<days>" switch for the "NewAreasFrom"
statement.
- OS/2: New parameters "Creation" and "Write" for the Touch
keyword. You can configure the type of "touch" you need.
Examples:
Touch ; default: touch the Creation (upload) date
Touch Creation ; same as default
Touch Write ; touch the Last Write date
Touch Creation Write ; touch both dates
- Fixed bug introduced in 2.32 which caused an access
violation in the "query" type commands if AreaDescWrap
was not used in the config file.
- Added check to prevent access violation when interactive
hatch is used with @diz and CompressCfg is NOT defined.
Now an error is reported.
- Added check to prevent that NEF reports "Empty command"
when no MaxAreaCompile statement is used.
- Enhanced INF Documentation.
2.33 Public Release, Mar 13 1996
- A bug in the squish.cfg parsing routines has been found:
if an area is defined with NOTHING after the path, this
area cannot be opened. The problem usually happens when
AreaTag specifies a *.MSG netmail with NO flags in
Squish.Cfg.
2.32 Public Release, Mar 13 1996
- New registration options: BMT Micro, NC, USA and Vince
Coen, UK.
- If the file description contains high ascii codes
(>127), the announcements will now contain remapped
plain-ASCII characters.
- You can allow High Ascii characters in some (or even
all) areas by the use of the "HighAsciiOk" statement in
the global or local-override announcement sections.
- New (global) statement: UniqueDmpLine.
Makes NEF generate FILES.DMP filebase files with
descriptions on one line only (multiple lines are
concatenated).
By default, NEF outputs multi-line descriptions without
changes to FILES.DMP: when using L)ocate and N)ewfiles
commands, Maximus will respect the original formatting,
but the continuation lines will be aligned to the left.
When this statement is used, the original formatting of
descriptions is lost (in the filebase) but Maximus will
be able to word-wrap and align when executing L)ocate or
N)ewfiles commands.
- Added check to prevent misconfiguration of the "AreaTag"
statement: it's ILLEGAL to use "AreaTag MyTag -$".
You must either use "AreaTag MyTag" (if SquishCfg is
used) or "AreaTag MyTag c:\bbs\mail\mytag -$".
In other words: when you let NEF lookup the TAG in
Squish.cfg, it is smart enough to find out the area type
on its own !
- When hatching from command line, it is now legal to specify
@diz without specifying a short description: it will be
considered empty. I still strongly recommend to always
specify a "short" description besides the optional "long"
one.
Example
Nef Hatch c:\file\filename.ext TAG @diz
is now equivalent to:
Nef Hatch c:\file\filename.ext TAG "" @diz
- Changed a typedef in NEFEAT.H, so that it does not
create problems with IBM compilers (thanks to Michael
Hohner).
- OS/2: New mnemonic characters for PmHatch PushButtons.
2.31 Private Beta, Mar 3 1996
- Fixed problem with UNC filenames that start with a double
backslash (on LANs).
2.30 Public Release, Feb 19 1996
- Check added to prevent NEF from issuing a forward request
to multiple uplinks for the same area, when a TAG is
contained in more than one Filebone file.
- New cfg statement: "ForwardWildReq".
Starting with ver 2.30, by default, TicFix requests with
wildcards are NOT forwarded to the filebones; this verb
enables even this type of request forward.
- Additional check in PmHatch: if no "short" description is
specified, the user is prompted about whether he really
means to hatch with no (short) description.
- Updated Docs.
2.26 Public Beta, Jan 22 1996
- COMPATIBILITY WARNING:
New override priority sequence for "from AKA".
The highest priority is that of the "Area AKA": if you
have defined an area aka (#<address> in FileArea
definition), it will always be the "from address" for
TICs from this area.
Then there is the aka override of "FileLink" definitions.
If a node has a "from aka" specified in it's FileLink
definition, it will be used for all TICs addressed to
this node, unless there is an overriding "Area AKA".
If no override is applicable from FileArea and FileLink
definitions, then an aka match is attempted: if the
"to-address" has a zone that matches an address defined
in NEF.CFG, then the first match is used.
If none of the previous cases applies, the primary
address is used (the first address defined in nef.cfg).
- New command line options for hatch commands.
"@bbs" can be used in the place of the normal
description: NEF will take (if existent) from the
files.bbs.
"@diz" can be used as a further optional parameter (after
the "short" description) to make NEF take the "long"
description from the file_id.diz contained in the
archive.